Mulakan

Cari dalam skrip untuk "THE SCRIPT"

SPYIWMQQ TABLEThis script is a multi-asset market bias dashboard for Pine Script v6, designed to provide a real-time health check of the major US indices (SPY, QQQ, and IWM) alongside technical levels on your chart. Core Functions Multi-Index Dashboard: It creates a table (optimized for a smaller size) that tracks the status of SPY, QQQ, and IWM simultaneously. Technical Alignment: It checks if each index is trading above or below its Fast, Mid, and Slow EMAs, as well as the VWAP. Bias Scoring: It calculates a "Net Bias" score for each symbol by weighting different technical criteria (EMAs, VWAP, and key price levels like Previous Day High/Low) to determine if the market is "Strong Bullish," "Bearish," or "Neutral". Automated Levels: The script automatically plots critical trading levels for the selected asset, including: Opening Range (ORB) high and low. Previous Day High (PDH) and Low (PDL) (supporting up to 5 days back). Premarket High (PMH) and Low (PML) for the current day. Key Features in this Version Compact UI: The table uses size.small for text and cell scaling to ensure it doesn't clutter your workspace while still providing data for all three indices. Adaptive Presets: It includes built-in profiles for Scalp, Trend, or Swing trading, which automatically adjust the EMA lengths and ORB timeframes to suit your style. Sentiment Triangles: It plots visual signals (up/down triangles) on the chart when the market bias reaches a specific strength threshold.
Penunjuk Pine Script®
oleh tashiakter36
Open Interest Bubbles [BackQuant]Open Interest Bubbles A visual OI positioning overlay that aggregates futures open interest across major venues, normalizes it into a consistent “signal strength” scale, then plots extreme events as bubbles, labels, and optional horizontal levels directly on price. What this is for Open interest is one of the cleanest ways to track when positioning is building, unwinding, or aggressively shifting. The problem is raw OI is noisy, exchange-specific, and hard to compare across time. This script solves that by: - Aggregating OI across multiple exchanges. - Letting you choose what “OI signal” you care about (raw, delta, percent versions). - Normalizing the signal so “big events” are easy to spot. - Plotting those events as bubbles and levels at the exact price they occurred. You end up with a clean, fast visual map of where large positioning changes occurred, and where those events may later matter as reaction points. ──────────────────────────────────────────────────────────── Plotting types (what you can display) Bubbles This mode plots OI events as size-bucketed circles on the chart. Bigger bubbles represent stronger normalized events. You can tune: - Bubble sizing by bucket (Tiny → Huge). - Heatmap vs solid color styling. - Signed vs unsigned coloring (positive/negative separation or magnitude-only). Best use: - Spotting “where something changed” at a glance. - Identifying clusters of positioning events around key price zones. - Seeing whether the market is repeatedly building/closing positions at similar levels. Levels Levels mode draws a horizontal line at the anchor price when an extreme OI event triggers. These act like “positioning memory” levels: - They do not claim to be support/resistance by themselves. - They highlight prices where the derivatives market clearly did something meaningful. Best use: - Marking potential reaction zones. - Combining with your price action tools (structure, OBs, FVGs) to confirm whether an OI level aligns with a technical level. - Building a “map” of where leverage likely entered or exited. Modes available in the script: - Off - Bubbles - Bubbles + Labels - Labels Only - Levels + Labels ──────────────────────────────────────────────────────────── Aggregated Open Interest source (multi-exchange) This indicator builds a single aggregated OI series by requesting OI data from multiple exchanges and summing it. You can toggle exchanges on/off: - Binance, Bybit, OKX, Bitget, Kraken, HTX, Deribit You can also choose OI units: - COIN , OI in base units (native sizing) - USD , converted for a dollar-value representation Important note: Not every symbol has OI data on every venue. If the script cannot build an aggregated series for the symbol, it will throw an error rather than quietly plotting garbage. ──────────────────────────────────────────────────────────── OI Source, what the bubbles are measuring You control what “signal” is normalized and plotted: - Delta , change in aggregated OI from the prior bar. Use when you want to highlight bursts of new positioning or sudden unwind events. - Raw OI , the aggregated open interest level itself. Use when you want to highlight absolute positioning build-up periods. - Delta % , percent change in OI. Use when you want moves normalized to the current OI regime, useful across different market eras. - Raw OI % , percent change form of the raw series. Use when you want relative changes rather than absolute size. Practical guidance: - Delta modes are best for “event detection”. - Raw modes are better for “regime context” and whether positioning is structurally rising or fading. ──────────────────────────────────────────────────────────── Normalization (the key to making it readable) Because OI varies massively across assets and time, the script includes multiple normalization modes to convert your chosen OI source into a comparable “strength” value. Options: - ZScore , deviation from a rolling mean in standard deviation units. - StdNorm , scaled by rolling standard deviation. - AbsZScore , absolute value version for magnitude-only mapping. - AbsStdNorm , absolute value version for magnitude-only mapping. - None , plots raw values (advanced users only, often too noisy visually). Why this matters: Normalization makes a “1.5” or “3.0” threshold mean something across different assets and timeframes, instead of being stuck to raw OI units. ──────────────────────────────────────────────────────────── Threshold system (when bubbles/levels trigger) The plot is driven by two user thresholds: - Base Threshold Controls where “meaningful” events start. Raising this reduces noise and focuses on larger deviations. - Extreme Threshold Controls what qualifies as a top-tier event. Extreme events are what you typically want to convert into labels and levels. You also control side filtering: - Both , show positive and negative events. - Positive Only , show only increases (or positive signal side depending on source). - Negative Only , show only decreases (or negative signal side). In practice: - Use Base Threshold to tune chart cleanliness. - Use Extreme Threshold to mark only the “big stuff” that tends to matter later. ──────────────────────────────────────────────────────────── Anchor Source (where the bubble/level is placed) The indicator places bubbles, labels, and levels at a price anchor you choose: - HL2, Close, Open, High, Low, VWAP This is important because “where you pin the event” changes how it reads: - Close is clean and consistent for backtesting and candle-close logic. - High/Low can better represent where the fight occurred intrabar. - VWAP can be useful for “fair price” anchoring in active markets. ──────────────────────────────────────────────────────────── Style system (theme, palette, signed logic) This script is built to look good and stay readable on busy charts. Themes - BackQuant, Classic, Ice, Fire, Mono, Custom Palette Mode - Solid , one consistent color - Heatmap , intensity increases with magnitude - Single Color Adaptive , adapts to chart background for clarity Side Coloring - Signed , positive and negative events can use different ramps - Unsigned , magnitude-only coloring Negative theme handling: - Auto (mirrors your chosen theme), - Invert (flips the ramp), - Custom (fully user-defined negative palette). What this gives you: - You can run a clean “mono” look for professional charts. - Or a high-contrast heatmap for fast scanning. - Or fully custom branding colors for BackQuant-style presentation. ──────────────────────────────────────────────────────────── Labels (what’s inside the label) When labels are enabled, the script can display: - OI , the aggregated OI value - OI + Norm , OI plus normalized strength - Norm Only , just the normalized strength - Src + Norm , the selected source value (Delta, Raw, %) plus normalized strength You can also control: - Left/Center/Right label alignment - Number formatting style (Raw, Compact, Volume format) Best practice: - Use “Src + Norm” when you want both the raw event size and its rarity. - Use “Norm Only” when you want a clean, minimal chart. ──────────────────────────────────────────────────────────── Levels and object limits (performance and cleanliness) Because this script draws objects, it includes a hard cleanup system: - You set Max Levels / Labels to control chart clutter. - The script deletes older lines/labels when the limit is exceeded. This is critical if you trade lower timeframes, where OI events can trigger frequently. ──────────────────────────────────────────────────────────── How to interpret the signals What a large bubble usually means: - A statistically large positioning change relative to recent history. - This can represent fresh leverage entering, forced liquidations, or aggressive de-risking, depending on direction and context. How to use levels: - Treat them as “attention levels”, not automatic entries. - Combine them with structure and liquidity tools: - If price revisits an OI level and shows rejection, it often confirms that level mattered. - If price slices through with no reaction, it often indicates the OI event was transitional, not defended. Common setups: - Clustered extreme bubbles near a breakout zone, then retest later. - Extreme negative event at capitulation low, followed by structure flip. - Extreme positive build into resistance, then unwind and mean reversion. Also, please check out @NoveltyTrade for the OI Aggregation logic & pulling the data source! Here is the original script:
Penunjuk Pine Script®
oleh BackQuant
1
[CASH] Crypto And Stocks Helper (MultiPack w. Alerts)ATTENTION! I'm not a good scripter. I have just learned a little basics for this project, stolen code from other public scripts and modified it, and gotten help from AI LLM's. If you want recognition from stolen code please tell me to give you the credit you deserve. The script is not completely finished yet and contains alot of errors but my friends and family wants access so I made it public. _________________________________________________________________________________ CASH has multiple indicators (a true all-in-one multipack), guides and alerts to help you make better trades/investments. It has: - Bitcoin Bull Market Support Band - Dollar Volume - 5 SMA and 5 EMA - HODL Trend (a.k.a SuperTrend) indicator - RSI, Volume and Divergence indicators w. alerts More to come as well, like Backburner and a POC line from Volume Profile. Everything is fully customizable, appearance and off/on etc. More information and explainations along with my guides you can find in settings under "Input" and "Style".
Penunjuk Pine Script®
oleh SenorBufoAlvarius
Mars Signals - Ultimate Institutional Suite v3.0(Joker)Comprehensive Trading Manual Mars Signals – Ultimate Institutional Suite v3.0 (Joker) ## Chapter 1 – Philosophy & System Architecture This script is not a simple “buy/sell” indicator. Mars Signals – UIS v3.0 (Joker) is designed as an institutional-style analytical assistant that layers several methodologies into a single, coherent framework. The system is built on four core pillars: 1. Smart Money Concepts (SMC) - Detection of Order Blocks (professional demand/supply zones). - Detection of Fair Value Gaps (FVGs) (price imbalances). 2. Smart DCA Strategy - Combination of RSI and Bollinger Bands - Identifies statistically discounted zones for scaling into spot positions or exiting shorts. 3. Volume Profile (Visible Range Simulation) - Distribution of volume by price, not by time. - Identification of POC (Point of Control) and high-/low-volume areas. 4. Wyckoff Helper – Spring - Detection of bear traps, liquidity grabs, and sharp bullish reversals. All four pillars feed into a Confluence Engine (Scoring System). The final output is presented in the Dashboard, with a clear, human-readable signal: - STRONG LONG 🚀 - WEAK LONG ↗ - NEUTRAL / WAIT - WEAK SHORT ↘ - STRONG SHORT 🩸 This allows the trader to see *how many* and *which* layers of the system support a bullish or bearish bias at any given time. ## Chapter 2 – Settings Overview ### 2.1 General & Dashboard Group - Show Dashboard Panel (`show_dash`) Turns the dashboard table in the corner of the chart ON/OFF. - Show Signal Recommendation (`show_rec`) - If enabled, the textual signal (STRONG LONG, WEAK SHORT, etc.) is displayed. - If disabled, you only see feature status (ON/OFF) and the current price. - Dashboard Position (`dash_pos`) Determines where the dashboard appears on the chart: - `Top Right` - `Bottom Right` - `Top Left` ### 2.2 Smart Money (SMC) Group - Enable SMC Strategy (`show_smc`) Globally enables or disables the Order Block and FVG logic. - Order Block Pivot Lookback (`ob_period`) Main parameter for detecting key pivot highs/lows (swing points). - Default value: 5 - Concept: A bar is considered a pivot low if its low is lower than the lows of the previous 5 and the next 5 bars. Similarly, a pivot high has a high higher than the previous 5 and the next 5 bars. These pivots are used as anchors for Order Blocks. - Increasing `ob_period`: - Fewer levels. - But levels tend to be more significant and reliable. - In highly volatile markets (major news, war events, FOMC, etc.), using values 7–10 is recommended to filter out weak levels. - Show Fair Value Gaps (`show_fvg`) Enables/disables the drawing of FVG zones (imbalances). - Bullish OB Color (`c_ob_bull`) - Color of Bullish Order Blocks (Demand Zones). - Default: semi-transparent green (transparency ≈ 80). - Bearish OB Color (`c_ob_bear`) - Color of Bearish Order Blocks (Supply Zones). - Default: semi-transparent red. - Bullish FVG Color (`c_fvg_bull`) - Color of Bullish FVG (upward imbalance), typically yellow. - Bearish FVG Color (`c_fvg_bear`) - Color of Bearish FVG (downward imbalance), typically purple. ### 2.3 Smart DCA Strategy Group - Enable DCA Zones (`show_dca`) Enables the Smart DCA logic and visual labels. - RSI Length (`rsi_len`) Lookback period for RSI (default: 14). - Shorter → more sensitive, more noise. - Longer → fewer signals, higher reliability. - Bollinger Bands Length (`bb_len`) Moving average period for Bollinger Bands (default: 20). - BB Multiplier (`bb_mult`) Standard deviation multiplier for Bollinger Bands (default: 2.0). - For extremely volatile markets, values like 2.5–3.0 can be used so that only extreme deviations trigger a DCA signal. ### 2.4 Volume Profile (Visible Range Sim) Group - Show Volume Profile (`show_vp`) Enables the simulated Volume Profile bars on the right side of the chart. - Volume Lookback Bars (`vp_lookback`) Number of bars used to compute the Volume Profile (default: 150). - Higher values → broader historical context, heavier computation. - Row Count (`vp_rows`) Number of vertical price segments (rows) to divide the total price range into (default: 30). - Width (%) (`vp_width`) Relative width of each volume bar as a percentage. In the code, bar widths are scaled relative to the row with the maximum volume. > Technical note: Volume Profile calculations are executed only on the last bar (`barstate.islast`) to keep the script performant even on higher timeframes. ### 2.5 Wyckoff Helper Group - Show Wyckoff Events (`show_wyc`) Enables detection and plotting of Wyckoff Spring events. - Volume MA Length (`vol_ma_len`) Length of the moving average on volume. A bar is considered to have Ultra Volume if its volume is more than 2× the volume MA. ## Chapter 3 – Smart Money Strategy (Order Blocks & FVG) ### 3.1 What Is an Order Block? An Order Block (OB) represents the footprint of large institutional orders: - Bullish Order Block (Demand Zone) The last selling region (bearish candle/cluster) before a strong upward move. - Bearish Order Block (Supply Zone) The last buying region (bullish candle/cluster) before a strong downward move. Institutions and large players place heavy orders in these regions. Typical price behavior: - Price moves away from the zone. - Later returns to the same zone to fill unfilled orders. - Then continues the larger trend. In the script: - If `pl` (pivot low) forms → a Bullish OB is created. - If `ph` (pivot high) forms → a Bearish OB is created. The box is drawn: - From `bar_index ` to `bar_index`. - Between `low ` and `high `. - `extend=extend.right` extends the OB into the future, so it acts as a dynamic support/resistance zone. - Only the last 4 OB boxes are kept to avoid clutter. ### 3.2 Order Block Color Guide - Semi-transparent Green (`c_ob_bull`) - Represents a Bullish Order Block (Demand Zone). - Interpretation: a price region with a high probability of bullish reaction. - Semi-transparent Red (`c_ob_bear`) - Represents a Bearish Order Block (Supply Zone). - Interpretation: a price region with a high probability of bearish reaction. Overlap (Multiple OBs in the Same Area) When two or more Order Blocks overlap: - The shared area appears visually denser/stronger. - This suggests higher order density. - Such zones can be treated as high-priority levels for entries, exits, and stop-loss placement. ### 3.3 Demand/Supply Logic in the Scoring Engine is_in_demand = low <= ta.lowest(low, 20) is_in_supply = high >= ta.highest(high, 20) - If current price is near the lowest lows of the last 20 bars, it is considered in a Demand Zone → positive impact on score. - If current price is near the highest highs of the last 20 bars, it is considered in a Supply Zone → negative impact on score. This logic complements Order Blocks and helps the Dashboard distinguish whether: - Market is currently in a statistically cheap (long-friendly) area, or - In a statistically expensive (short-friendly) area. ### 3.4 Fair Value Gaps (FVG) #### Concept When the market moves aggressively: - Some price levels are skipped and never traded. - A gap between wicks/shadows of consecutive candles appears. - These regions are called Fair Value Gaps (FVGs) or Imbalances. The market generally “dislikes” imbalance and often: - Returns to these zones in the future. - Fills the gap (rebalance). - Then resumes its dominant direction. #### Implementation in the Code Bullish FVG (Yellow) fvg_bull_cond = show_smc and show_fvg and low > high and close > high if fvg_bull_cond box.new(bar_index , high , bar_index, low, ...) Core condition: `low > high ` → the current low is above the high of two bars ago; the space between them is an untraded gap. Bearish FVG (Purple) fvg_bear_cond = show_smc and show_fvg and high < low and close < low if fvg_bear_cond box.new(bar_index , low , bar_index, high, ...) Core condition: `high < low ` → the current high is below the low of two bars ago; again a price gap exists. #### FVG Color Guide - Transparent Yellow (`c_fvg_bull`) – Bullish FVG Often acts like a magnet for price: - Price tends to retrace into this zone, - Fill the imbalance, - And then continue higher. - Transparent Purple (`c_fvg_bear`) – Bearish FVG Price tends to: - Retrace upward into the purple area, - Fill the imbalance, - And then resume downward movement. #### Trading with FVGs - FVGs are *not* standalone entry signals. They are best used as: - Targets (take-profit zones), or - Reaction areas where you expect a pause or reversal. Examples: - If you are long, a bearish FVG above is often an excellent take-profit zone. - If you are short, a bullish FVG below is often a good cover/exit zone. ### 3.5 Core SMC Trading Templates #### Reversal Long 1. Price trades down into a green Order Block (Demand Zone). 2. A bullish confirmation candle (Close > Open) forms inside or just above the OB. 3. If this zone is close to or aligned with a bullish FVG (yellow), the signal is reinforced. 4. Entry: - At the close of the confirmation candle, or - Using a limit order near the upper boundary of the OB. 5. Stop-loss: - Slightly below the OB. - If the OB is broken decisively and price consolidates below it, the zone loses validity. 6. Targets: - The next FVG, - Or the next red Order Block (Supply Zone) above. #### Reversal Short The mirror scenario: - Price rallies into a red Order Block (Supply). - A bearish confirmation candle forms (Close < Open). - FVG/premium structure above can act as a confluence. - Stop-loss goes above the OB. - Targets: lower FVGs or subsequent green OBs below. ## Chapter 4 – Smart DCA Strategy (RSI + Bollinger Bands) ### 4.1 Smart DCA Concept - Classic DCA = buying at fixed time intervals regardless of price. - Smart DCA = scaling in only when: - Price is statistically cheaper than usual, and - The market is in a clear oversold condition. Code logic: rsi_val = ta.rsi(close, rsi_len) = ta.bb(close, bb_len, bb_mult) dca_buy = show_dca and rsi_val < 30 and close < bb_lower dca_sell = show_dca and rsi_val > 70 and close > bb_upper Conditions: - DCA Buy – Smart Scale-In Zone - RSI < 30 → oversold. - Close < lower Bollinger Band → price has broken below its typical volatility envelope. - DCA Sell – Overbought/Distribution Zone - RSI > 70 → overbought. - Close > upper Bollinger Band → price is extended far above the mean. ### 4.2 Visual Representation on the Chart - Green “DCA” Label Below Candle - Shape: `labelup`. - Color: lime background, white text. - Meaning: statistically attractive level for laddered spot entries or short exits. - Red “SELL” Label Above Candle - Warning that the market is in an extended, overbought condition. - Suitable for profit-taking on longs or considering short entries (with proper confluence and risk management). - Light Green Background (`bgcolor`) - When `dca_buy` is true, the candle background turns very light green (high transparency). - This helps visually identify DCA Zones across the chart at a glance. ### 4.3 Practical Use in Trading #### Spot Trading Used to build a better average entry price: - Every time a DCA label appears, allocate a fixed portion of capital (e.g., 2–5%). - Combining DCA signals with: - Green OBs (Demand Zones), and/or - The Volume Profile POC makes the zone structurally more important. #### Futures Trading - Longs - Use DCA Buy signals as low-risk zones for opening or adding to longs when: - Price is inside a green OB, or - The Dashboard already leans LONG. - Shorts - Use DCA Sell signals as: - Exit zones for longs, or - Areas to initiate shorts with stops above structural highs. ## Chapter 5 – Volume Profile (Visible Range Simulation) ### 5.1 Concept Traditional volume (histogram under the chart) shows volume over time. Volume Profile shows volume by price level: - At which prices has the highest trading activity occurred? - Where did buyers and sellers agree the most (High Volume Nodes – HVNs)? - Where did price move quickly due to low participation (Low Volume Nodes – LVNs)? ### 5.2 Implementation in the Script Executed only when `show_vp` is enabled and on the last bar: 1. The last `vp_lookback` bars (default 150) are processed. 2. The minimum low and maximum high over this window define the price range. 3. This price range is divided into `vp_rows` segments (e.g., 30 rows). 4. For each row: - All bars are scanned. - If the mid-price `(high + low ) / 2` falls inside a row, that bar’s volume is added to the row total. 5. The row with the greatest volume is stored as `max_vol_idx` (the POC row). 6. For each row, a volume box is drawn on the right side of the chart. ### 5.3 Color Scheme - Semi-transparent Orange - The row with the maximum volume – the Point of Control (POC). - Represents the strongest support/resistance level from a volume perspective. - Semi-transparent Blue - Other volume rows. - The taller the bar → the higher the volume → the stronger the interest at that price band. ### 5.4 Trading Applications - If price is above POC and retraces back into it: → POC often acts as support, suitable for long setups. - If price is below POC and rallies into it: → POC often acts as resistance, suitable for short setups or profit-taking. HVNs (Tall Blue Bars) - Represent areas of equilibrium where the market has spent time and traded heavily. - Price tends to consolidate here before choosing a direction. LVNs (Short or Nearly Empty Bars) - Represent low participation zones. - Price often moves quickly through these areas – useful for targeting fast moves. ## Chapter 6 – Wyckoff Helper – Spring ### 6.1 Spring Concept In the Wyckoff framework: - A Spring is a false break of support. - The market briefly trades below a well-defined support level, triggers stop losses, then sharply reverses upward as institutional buyers absorb liquidity. This movement: - Clears out weak hands (retail sellers). - Provides large players with liquidity to enter long positions. - Often initiates a new uptrend. ### 6.2 Code Logic Conditions for a Spring: 1. The current low is lower than the lowest low of the previous 50 bars → apparent break of a long-standing support. 2. The bar closes bullish (Close > Open) → the breakdown was rejected. 3. Volume is significantly elevated: → `volume > 2 × volume_MA` (Ultra Volume). When all conditions are met and `show_wyc` is enabled: - A pink diamond is plotted below the bar, - With the label “Spring” – one of the strongest long signals in this system. ### 6.3 Trading Use - After a valid Spring, markets frequently enter a meaningful bullish phase. - The highest quality setups occur when: - The Spring forms inside a green Order Block, and - Near or on the Volume Profile POC. Entries: - At the close of the Spring bar, or - On the first pullback into the mid-range of the Spring candle. Stop-loss: - Slightly below the Spring’s lowest point (wick low plus a small buffer). ## Chapter 7 – Confluence Engine & Dashboard ### 7.1 Scoring Logic For each bar, the script: 1. Resets `score` to 0. 2. Adjusts the score based on different signals. SMC Contribution if show_smc if is_in_demand score += 1 if is_in_supply score -= 1 - Being in Demand → `+1` - Being in Supply → `-1` DCA Contribution if show_dca if dca_buy score += 2 if dca_sell score -= 2 - DCA Buy → `+2` (strong, statistically driven long signal) - DCA Sell → `-2` Wyckoff Spring Contribution if show_wyc if wyc_spring score += 2 - Spring → `+2` (entry of strong money) ### 7.2 Mapping Score to Dashboard Signal - score ≥ 2 → STRONG LONG 🚀 Multiple bullish conditions aligned. - score = 1 → WEAK LONG ↗ Some bullish bias, but only one layer clearly positive. - score = 0 → NEUTRAL / WAIT Rough balance between buying and selling forces; staying flat is usually preferable. - score = -1 → WEAK SHORT ↘ Mild bearish bias, suited for cautious or short-term plays. - score ≤ -2 → STRONG SHORT 🩸 Convergence of several bearish signals. ### 7.3 Dashboard Structure The dashboard is a two-column table: - Row 0 - Column 0: `"Mars Signals"` – black background, white text. - Column 1: `"UIS v3.0"` – black background, yellow text. - Row 1 - Column 0: `"Price:"` (light grey background). - Column 1: current closing price (`close`) with a semi-transparent blue background. - Row 2 - Column 0: `"SMC:"` - Column 1: - `"ON"` (green) if `show_smc = true` - `"OFF"` (grey) otherwise. - Row 3 - Column 0: `"DCA:"` - Column 1: - `"ON"` (green) if `show_dca = true` - `"OFF"` (grey) otherwise. - Row 4 - Column 0: `"Signal:"` - Column 1: signal text (`status_txt`) with background color `status_col` (green, red, teal, maroon, etc.) - If `show_rec = false`, these cells are cleared. ## Chapter 8 – Visual Legend (Colors, Shapes & Actions) For quick reading inside TradingView, the visual elements are described line by line instead of a table. Chart Element: Green Box Color / Shape: Transparent green rectangle Core Meaning: Bullish Order Block (Demand Zone) Suggested Trader Response: Look for longs, Smart DCA adds, closing or reducing shorts. Chart Element: Red Box Color / Shape: Transparent red rectangle Core Meaning: Bearish Order Block (Supply Zone) Suggested Trader Response: Look for shorts, or take profit on existing longs. Chart Element: Yellow Area Color / Shape: Transparent yellow zone Core Meaning: Bullish FVG / upside imbalance Suggested Trader Response: Short take-profit zone or expected rebalance area. Chart Element: Purple Area Color / Shape: Transparent purple zone Core Meaning: Bearish FVG / downside imbalance Suggested Trader Response: Long take-profit zone or temporary supply region. Chart Element: Green "DCA" Label Color / Shape: Green label with white text, plotted below the candle Core Meaning: Smart ladder-in buy zone, DCA buy opportunity Suggested Trader Response: Spot DCA entry, partial short exit. Chart Element: Red "SELL" Label Color / Shape: Red label with white text, plotted above the candle Core Meaning: Overbought / distribution zone Suggested Trader Response: Take profit on longs, consider initiating shorts. Chart Element: Light Green Background (bgcolor) Color / Shape: Very transparent light-green background behind bars Core Meaning: Active DCA Buy zone Suggested Trader Response: Treat as a discount zone on the chart. Chart Element: Orange Bar on Right Color / Shape: Transparent orange horizontal bar in the volume profile Core Meaning: POC – price with highest traded volume Suggested Trader Response: Strong support or resistance; key reference level. Chart Element: Blue Bars on Right Color / Shape: Transparent blue horizontal bars in the volume profile Core Meaning: Other volume levels, showing high-volume and low-volume nodes Suggested Trader Response: Use to identify balance zones (HVN) and fast-move corridors (LVN). Chart Element: Pink "Spring" Diamond Color / Shape: Pink diamond with white text below the candle Core Meaning: Wyckoff Spring – liquidity grab and potential major bullish reversal Suggested Trader Response: One of the strongest long signals in the suite; look for high-quality long setups with tight risk. Chart Element: STRONG LONG in Dashboard Color / Shape: Green background, white text in the Signal row Core Meaning: Multiple bullish layers in confluence Suggested Trader Response: Consider initiating or increasing longs with strict risk management. Chart Element: STRONG SHORT in Dashboard Color / Shape: Red background, white text in the Signal row Core Meaning: Multiple bearish layers in confluence Suggested Trader Response: Consider initiating or increasing shorts with a logical, well-placed stop. ## Chapter 9 – Timeframe-Based Trading Playbook ### 9.1 Timeframe Selection - Scalping - Timeframes: 1M, 5M, 15M - Objective: fast intraday moves (minutes to a few hours). - Recommendation: focus on SMC + Wyckoff. Smart DCA on very low timeframes may introduce excessive noise. - Day Trading - Timeframes: 15M, 1H, 4H - Provides a good balance between signal quality and frequency. - Recommendation: use the full stack – SMC + DCA + Volume Profile + Wyckoff + Dashboard. - Swing Trading & Position Investing - Timeframes: Daily, Weekly - Emphasis on Smart DCA + Volume Profile. - SMC and Wyckoff are used mainly to fine-tune swing entries within larger trends. ### 9.2 Scenario A – Scalping Long Example: 5-Minute Chart 1. Price is declining into a green OB (Bullish Demand). 2. A candle with a long lower wick and bullish close (Pin Bar / Rejection) forms inside the OB. 3. A Spring diamond appears below the same candle → very strong confluence. 4. The Dashboard shows at least WEAK LONG ↗, ideally STRONG LONG 🚀. 5. Entry: - On the close of the confirmation candle, or - On the first pullback into the mid-range of that candle. 6. Stop-loss: - Slightly below the OB. 7. Targets: - Nearby bearish FVG above, and/or - The next red OB. ### 9.3 Scenario B – Day-Trading Short Recommended Timeframes: 1H or 4H 1. The market completes a strong impulsive move upward. 2. Price enters a red Order Block (Supply). 3. In the same zone, a purple FVG appears or remains unfilled. 4. On a lower timeframe (e.g., 15M), RSI enters overbought territory and a DCA Sell signal appears. 5. The main timeframe Dashboard (1H) shows WEAK SHORT ↘ or STRONG SHORT 🩸. Trade Plan - Open a short near the upper boundary of the red OB. - Place the stop above the OB or above the last swing high. - Targets: - A yellow FVG lower on the chart, and/or - The next green OB (Demand) below. ### 9.4 Scenario C – Swing / Investment with Smart DCA Timeframes: Daily / Weekly 1. On the daily or weekly chart, each time a green “DCA” label appears: - Allocate a fixed fraction of your capital (e.g., 3–5%) to that asset. 2. Check whether this DCA zone aligns with the orange POC of the Volume Profile: - If yes → the quality of the entry zone is significantly higher. 3. If the DCA signal sits inside a daily green OB, the probability of a medium-term bottom increases. 4. Always build the position laddered, never all-in at a single price. Exits for investors: - Near weekly red OBs or large purple FVG zones. - Ideally via partial profit-taking rather than closing 100% at once. ### 9.5 Case Study 1 – BTCUSDT (15-Minute) - Context: Price has sold off down towards 65,000 USD. - A green OB had previously formed at that level. - Near the lower boundary of this OB, a partially filled yellow FVG is present. - As price returns to this region, a Spring appears. - The Dashboard shifts from NEUTRAL / WAIT to WEAK LONG ↗. Plan - Enter a long near the OB low. - Place stop below the Spring low. - First target: a purple FVG around 66,200. - Second (optional) target: the first red OB above that level. ### 9.6 Case Study 2 – Meme Coin (PEPE – 4H) - After a strong pump, price enters a corrective phase. - On the 4H chart, RSI drops below 30; price breaks below the lower Bollinger Band → a DCA label prints. - The Volume Profile shows the POC at approximately the same level. - The Dashboard displays STRONG LONG 🚀. Plan - Execute laddered buys in the combined DCA + POC zone. - Place a protective stop below the last significant swing low. - Target: an expected 20–30% upside move towards the next red OB or purple FVG. ## Chapter 10 – Risk Management, Psychology & Advanced Tuning ### 10.1 Risk Management No signal, regardless of its strength, replaces risk control. Recommendations: - In futures, do not expose more than 1–3% of account equity to risk per trade. - Adjust leverage to the volatility of the instrument (lower leverage for highly volatile altcoins). - Place stop-losses in zones where the idea is clearly invalidated: - Below/above the relevant Order Block or Spring, not randomly in the middle of the structure. ### 10.2 Market-Specific Parameter Tuning - Calmer Markets (e.g., major FX pairs) - `ob_period`: 3–5. - `bb_mult`: 2.0 is usually sufficient. - Highly Volatile Markets (Crypto, news-driven assets) - `ob_period`: 7–10 to highlight only the most robust OBs. - `bb_mult`: 2.5–3.0 so that only extreme deviations trigger DCA. - `vol_ma_len`: increase (e.g., to ~30) so that Spring triggers only on truly exceptional volume spikes. ### 10.3 Trading Psychology - STRONG LONG 🚀 does not mean “risk-free”. It means the probability of a successful long, given the model’s logic, is higher than average. - Treat Mars Signals as a confirmation and context system, not a full replacement for your own decision-making. - Example of disciplined thinking: - The Dashboard prints STRONG LONG, - But price is simultaneously testing a multi-month macro resistance or a major negative news event is imminent, - In such cases, trade smaller, widen stops appropriately, or skip the trade. ## Chapter 11 – Technical Notes & FAQ ### 11.1 Does the Script Repaint? - Order Blocks and Springs are based on completed pivot structures and confirmed candles. - Until a pivot is confirmed, an OB does not exist; after confirmation, behavior is stable under classic SMC assumptions. - The script is designed to be structurally consistent rather than repainting signals arbitrarily. ### 11.2 Computational Load of Volume Profile - On the last bar, the script processes up to `vp_lookback` bars × `vp_rows` rows. - On very low timeframes with heavy zooming, this can become demanding. - If you experience performance issues: - Reduce `vp_lookback` or `vp_rows`, or - Temporarily disable Volume Profile (`show_vp = false`). ### 11.3 Multi-Timeframe Behavior - This version of the script is not internally multi-timeframe. All logic (OB, DCA, Spring, Volume Profile) is computed on the active timeframe only. - Practical workflow: - Analyze overall structure and key zones on higher timeframes (4H / Daily). - Use lower timeframes (15M / 1H) with the same tool for timing entries and exits. ## Conclusion Mars Signals – Ultimate Institutional Suite v3.0 (Joker) is a multi-layer trading framework that unifies: - Price structure (Order Blocks & FVG), - Statistical behavior (Smart DCA via RSI + Bollinger), - Volume distribution by price (Volume Profile with POC, HVN, LVN), - Liquidity events (Wyckoff Spring), into a single, coherent system driven by a transparent Confluence Scoring Engine. The final output is presented in clear, actionable language: > STRONG LONG / WEAK LONG / NEUTRAL / WEAK SHORT / STRONG SHORT The system is designed to support professional decision-making, not to replace it. Used together with strict risk management and disciplined execution, Mars Signals – UIS v3.0 (Joker) can serve as a central reference manual and operational guide for your trading workflow, from scalping to swing and investment positioning.
Penunjuk Pine Script®
oleh MarsSignals
[blackcat] L1 Value Trend IndicatorOVERVIEW The L1 Value Trend Indicator is a sophisticated technical analysis tool designed for TradingView users seeking advanced market trend identification and trading signals. This comprehensive indicator combines multiple analytical techniques to provide traders with a holistic view of market dynamics, helping identify potential entry and exit points through various signal mechanisms. 📈 It features a main Value Trend line along with a lagged version, golden cross and dead cross signals, and multiple technical indicators including RSI, Williams %R, Stochastic %K/D, and Relative Strength calculations. The indicator also includes reference levels for support and resistance analysis, making it a versatile tool for both short-term and long-term trading strategies. ✅ FEATURES 📈 Primary Value Trend Line: Calculates a smoothed value trend using a combination of SMA and custom smoothing techniques 🔍 Value Trend Lag: Implements a lagged version of the main trend line for cross-over analysis 🚀 Golden Cross & Dead Cross Signals: Identifies buy/sell opportunities when the main trend line crosses its lagged version 💸 Multi-Indicator Integration: Combines multiple technical analysis tools for comprehensive market view 📊 RSI Calculations: Includes 6-period, 7-period, and 13-period RSI calculations for momentum analysis 📈 Williams %R: Provides overbought/oversold conditions using the Williams %R formula 📉 Stochastic Oscillator: Implements both Stochastic %K and %D calculations for momentum confirmation 📋 Relative Strength: Calculates relative strength based on highest highs and current price ✅ Visual Labels: Displays BUY and SELL labels on chart when crossover conditions are met 📣 Alert Conditions: Provides automated alert conditions for golden cross and dead cross events 📌 Reference Levels: Plots entry (25) and exit (75) reference lines for support/resistance analysis HOW TO USE Copy the Script: Copy the complete Pine Script code from the original file Open TradingView: Navigate to TradingView website or application Access Pine Editor: Go to the Pine Script editor (usually found in the chart toolbar) Paste Code: Paste the copied script into the editor Save Script: Save the script with a descriptive name like " L1 Value Trend Indicator" Select Chart: Choose the chart where you want to apply the indicator Add Indicator: Apply the indicator to your chart Configure Parameters: Adjust input parameters to customize behavior Monitor Signals: Watch for golden cross (BUY) and dead cross (SELL) signals Use Reference Levels: Monitor entry (25) and exit (75) lines for support/resistance levels LIMITATIONS ⚠️ Potential Repainting: The script may repaint due to lookahead bias in some calculations 📉 Lookahead Bias: Some calculations may reference future values, potentially causing repainting issues 🔄 Parameter Sensitivity: Results may vary significantly with different parameter settings 📉 Computational Complexity: May impact chart performance with heavy calculations on large datasets 📊 Resource Usage: Requires significant processing power for multiple indicator calculations 🔄 Data Sensitivity: Results may be affected by data quality and market conditions NOTES 📈 Signal Timing: Cross-over signals may lag behind actual price movements 📉 Parameter Optimization: Optimal parameters may vary by market conditions and asset type 📋 Market Conditions: Performance may vary significantly across different market environments 📈 Multi-Indicator: Combine signals with other technical indicators for confirmation 📉 Timeframe Analysis: Use multiple timeframes for enhanced signal accuracy 📋 Volume Analysis: Incorporate volume data for additional confirmation 📈 Strategy Integration: Consider using this indicator as part of a broader trading strategy 📉 Risk Management: Use signals as part of a comprehensive risk management approach 📋 Backtesting: Test parameter combinations with historical data before live trading THANKS 🙏 Original Creator: blackcat1402 creates the L1 Value Trend Indicator 📚 Community Contributions: Recognition to TradingView community for continuous improvements and contributions 📈 Collaborative Development: Appreciation for collaborative efforts in enhancing technical analysis tools 📉 TradingView Community: Special thanks to TradingView community members for their ongoing support and feedback 📋 Educational Resources: Recognition of educational resources that helped in understanding technical analysis principles
Penunjuk Pine Script®
oleh blackcat1402
weighted support or resistance linesQ: Why should users choose this script? A: I found that in all the publicly available scripts about support and resistance lines, there is basically no weight identification for these lines. In other words, users do not know which support or resistance lines are the most important. So I specifically wrote this script. 1. By adjusting the weights, only the most effective support or resistance lines are displayed. (Length threshold of trend price (Bar)) 2. By selecting the number of K-lines, only the latest number of support or resistance lines generated will be displayed. (Maximum number of reserved S/R lines) 3. By selecting whether to automatically remove lines, only support or resistance lines that have not been penetrated by the k-line will be displayed. If this function is checked, the weight can be adjusted lower, as high-weight SR may have already been penetrated, and the newly generated SR may have a lower weight. (Automatically remove lines penetrated by closing price confirmation) 4. Notes: The default parameters work well in 15-minute candlestick charts. For candlestick charts with other time periods, the parameters can be adjusted appropriately. It is suitable for sideways trading but not for strong trends. 5. I'm quite satisfied with the performance of the script, as I specifically optimized it, lol
Penunjuk Pine Script®
oleh zbgubymy112
Trend with ADX/EMA - Buy & Sell SignalsThis script is designed to help traders make buy and sell decisions based on trend analysis using two key methods: ADX (Average Directional Index) and EMA (Exponential Moving Averages). Here's a breakdown in simple terms: What Does It Do? Identifies the Trend's Strength and Direction: Uses the ADX indicator to determine how strong the trend is. Compares two lines (DI+ and DI−) to identify whether the trend is moving up or down. Generates Buy and Sell Signals: Uses two EMAs (a fast one and a slow one) to check when the price crosses key levels, signaling a possible buy or sell opportunity. Plots visual indicators (arrows and labels) for easy interpretation. Color-Codes the Chart: Highlights the background in green when the trend is bullish (uptrend). Highlights the background in red when the trend is bearish (downtrend). Alerts the User: Creates alerts when specific conditions for buying or selling are met. Key Components: 1. ADX (Trend Strength & Direction) What is ADX? ADX measures how strong the trend is (not the direction). Higher ADX means a stronger trend. It also calculates two lines: DI+: Measures upward movement strength. DI−: Measures downward movement strength. How It Works in the Script: If DI+ is greater than DI−, it’s a bullish trend (upward). If DI− is greater than DI+, it’s a bearish trend (downward). The background turns green for an uptrend and red for a downtrend. 2. EMA (Buy and Sell Decisions) What is EMA? EMA is a moving average that gives more weight to recent prices. It’s used to smooth out price fluctuations. How It Works in the Script: The script calculates two EMAs: Fast EMA (short-term average): Reacts quickly to price changes. Slow EMA (long-term average): Reacts slower and shows overall trends. When the Fast EMA crosses above the Slow EMA, it’s a signal to Buy. When the Fast EMA crosses below the Slow EMA, it’s a signal to Sell. These signals are marked on the chart as "Buy" and "Sell" labels. 3. Buy and Sell Alerts The script sets up alerts for the user: Buy Alert: When a crossover indicates a bullish signal. Sell Alert: When a crossunder indicates a bearish signal. Visual Elements on the Chart: Background Colors: Green: When the DI+ line indicates an uptrend. Red: When the DI− line indicates a downtrend. EMA Lines: Green Line: Fast EMA. Red Line: Slow EMA. Buy/Sell Labels: "Buy" label: Shown when the Fast EMA crosses above the Slow EMA. "Sell" label: Shown when the Fast EMA crosses below the Slow EMA. Why Use This Script? Trend Analysis: Helps you quickly identify the strength and direction of the market trend. Buy/Sell Signals: Gives clear signals to enter or exit trades based on trend and EMA crossovers. Custom Alerts: Ensures you never miss a trading opportunity by notifying you when conditions are met. Visual Simplicity: Makes it easy to interpret trading signals with color-coded backgrounds and labeled arrows.
Penunjuk Pine Script®
oleh RMPM
Volatility Signaling 50SMAOverview of the Script: The script implements a volatility signaling indicator using a 50-period Simple Moving Average (SMA). It incorporates Bollinger Bands and the Average True Range (ATR) to dynamically adjust the SMA's color based on volatility conditions. Here's a detailed breakdown: Components of the Script: 1. Inputs: The script allows the user to customize key parameters for flexibility: Bollinger Bands Length (length): Determines the period for calculating the Bollinger Bands. Source (src): The price data to use, defaulting to the closing price. Standard Deviation Multiplier (mult): Scales the Bollinger Bands' width. ATR Length (atrLength): Sets the period for calculating the ATR. The 50-period SMA length (smaLength) is fixed at 50. 2. Bollinger Bands Calculation: Basis: Calculated as the SMA of the selected price source over the specified length. Upper and Lower Bands: Determined by adding/subtracting a scaled standard deviation (dev) from the basis. 3. ATR Calculation: Computes the Average True Range over the user-defined atrLength. 4. Volatility-Based Conditions: The script establishes thresholds for Bollinger Band width relative to ATR: Yellow Condition: When the band width (upper - lower) is less than 1.25 times the ATR. Orange Condition: When the band width is less than 1.5 times the ATR. Red Condition: When the band width is less than 1.75 times the ATR. 5. Dynamic SMA Coloring: The 50-period SMA is colored based on the above conditions: Yellow: Indicates relatively low volatility. Orange: Indicates moderate volatility. Red: Indicates higher volatility. White: Default color when no conditions are met. 6. Plotting the 50-Period SMA: The script plots the SMA (sma50) with a dynamically assigned color, enabling visual analysis of market conditions. Use Case: This script is ideal for traders seeking to assess market volatility and identify changes using Bollinger Bands and ATR. The colored SMA provides an intuitive way to gauge market dynamics directly on the chart. Example Visualization: Yellow SMA: The market is in a low-volatility phase. Orange SMA: Volatility is picking up but remains moderate. Red SMA: Higher volatility, potentially signaling significant market activity. White SMA: Neutral/default state.
Penunjuk Pine Script®
oleh MoneyPrintingCompany
Previous High and Low Count with Probabilities + Risk On/Off1. Purpose of the Script: This trading script combines two important concepts: Previous High and Low Count: It tracks whether the current price exceeds the previous day’s high or low and calculates probabilities for the next price movement (up or down). Risk On / Risk Off Indicator: It evaluates market sentiment through various indicators (such as the Fear & Greed Index, VIX, and others) and shows whether the market is in a risk-on or risk-off state. This information impacts the probabilities of price movement. 2. How it Works: Previous High and Low: The script tracks how often the price exceeds the previous day’s high or low and calculates the probability of an upward or downward movement based on that. This gives you an idea of how often the market reacts at the previous day's high or low. Risk On / Risk Off: Based on various market factors (Fear & Greed Index, VIX, Put-Call Ratio, etc.), the script calculates the Risk On or Risk Off state. In Risk On, the probability of an upward movement increases, and the probability of a downward movement decreases. In Risk Off, it’s the opposite. Adjusted Probabilities: The probabilities for an Up or Down movement are adjusted based on the current Risk On / Risk Off state. In a Risk On environment, the probability for an upward move increases, while in a Risk Off environment, the probability for a downward move increases. 3. How to Use the Script: Add the Script in TradingView: TradingView: Click on "Add to Chart" to apply the script to your chart. Manual Input of Indicators: For the Fear & Greed Index, VIX, and other indicators, you need to manually enter the current values. You can get these values from various publicly available sources: Fear & Greed Index: CNN Fear & Greed Index VIX (Volatility Index): VIX Index Other indicators like Put-Call Ratio, Bitcoin Volatility, Oil Prices, and US Dollar Index can also be manually inputted, and they can be found on finance websites like Yahoo Finance, MarketWatch, and Bloomberg. Observe the Colors and Symbols: If the market is in a Risk On state, the background will turn green, and a green triangle will appear below the candle. If the market is in a Risk Off state, the background will turn red, and a red triangle will appear above the candle. Track the Probabilities: A label will appear on the chart showing the calculated probabilities for Up and Down movements. These probabilities are adjusted based on the current market state (Risk On/Off). 4. Meaning of the Probabilities: Up Probability: Indicates the probability that the price will rise. Down Probability: Indicates the probability that the price will fall. The probabilities are dynamic and adjust based on the Risk On / Risk Off state, helping you make better decisions based on the current market conditions.
Penunjuk Pine Script®
oleh morris220768
Johnny's Moving Average RibbonProps to Madrid for creating the original script: Madrid Moving Average Ribbon. All I did was upgrade it to pinescript v5 and added a few changes to the script. Features and Functionality Moving Average Types: The indicator offers a choice between exponential moving averages (EMAs) and simple moving averages (SMAs), allowing users to select the type that best fits their trading strategy. Dynamic Color Coding: Each moving average line within the ribbon changes color based on its direction and position relative to a reference moving average, providing visual cues for market sentiment and trend strength. Lime Green: Indicates an uptrend and potential long positions, shown when a moving average is rising and above the longer-term reference MA. Maroon: Suggests caution for long positions or potential short reentry points, displayed when a moving average is rising but below the reference MA. Ruby Red: Represents a downtrend, suitable for short positions, shown when a moving average is falling and below the reference MA. Green: Signals potential reentry points for downtrends or warnings for uptrend reversals, displayed when a moving average is falling but above the reference MA. Usage and Application Trend Identification: Traders can quickly ascertain the market's direction at a glance by observing the predominant color of the ribbon and its orientation. Trade Entry and Exit Points: The color transitions within the ribbon can signal potential entry or exit points, with changes from green to lime or red to maroon indicating shifts in market momentum. Customization: Users have the flexibility to toggle between exponential and simple moving averages, allowing for a tailored analytical approach that aligns with their individual trading preferences. Technical Specifications The ribbon consists of multiple moving averages calculated over different periods, typically ranging from shorter to longer-term intervals to capture various aspects of market behavior. The color dynamics are determined by comparing each moving average to a reference point, often a longer-term moving average within the ribbon, to assess the relative trend strength and direction.
Penunjuk Pine Script®
oleh JonathanLeyva
Ema Short Long Indicator[CHE]█ CONCEPTS This Pine Script is an EMA Short Long indicator that displays the crossing EMA lines on the chart. The indicator uses three exponential moving averages (EMAs) to generate the buy and sell signals. The EMA lines are plotted as green (uptrend) and red (downtrend) lines. When the green line is above the white signal line, the indicator generates a buy signal, when the green line is below the white signal line, the indicator generates a sell signal. Arrows are also displayed marking the buy and sell signals. There is also an option to allow indicator repainting or not. Finally, users can also set alerts to be alerted to potential trading opportunities. Note: please do not disable "time frame gaps". Allows to calculate the indicator on a Timeframe (TF) different from that of the chart Time window. The TF should ideally be higher than the charts to provide a broader perspective than the TF of the chart. Using TFs lower than the chart's will deliver fragmentary results, since only the last value of intrabar is displayed (multiple values cannot be displayed for a single chart bar). The Gaps setting determines the behavior when the TF is higher than the TF of the chart. If 'gaps' is checked, higher TF values only come in and are interconnected on the diagram when the higher TF completed. This has the advantage of avoidance Real-time epainting. If Gaps is not enabled, Gaps are filled with the last higher TF value calculated, which will not produce a repaint Values on historical bars but repaint values realtime. █  HOW TO USE IT Load the indicator on an active chart (see the Help Center if you don't know how). Time period By default, the script uses an auto-stepping mechanism to adjust the time period of its moving window to the chart's timeframe. The following table shows chart timeframes and the corresponding time period used by the script. When the chart's timeframe is less than or equal to the timeframe in the first column, the second column's time period is used to calculate the Ema Short Long Indicator : Chart Time timeframe period 1min 🠆 1H 5min 🠆 4H 1H 🠆 1D 4H 🠆 3D 12H 🠆 1W 1D 🠆 1M 1W 🠆 ​3M █  DESCRIPTION The script begins by setting up the chart indicator with a short title, "ESLI", and enabling it as an overlay. It then initializes several variables for time conversions, to be used later in the script. The timeStep_translate() function converts the timeframe of the chart into a string representing a larger time interval, based on the number of seconds in the timeframe. The resulting string is used to label the horizontal axis of the chart. Next, the script defines several input variables that can be modified by the user. These include the colors of the EMA lines and the signals, whether or not the indicator is allowed to repaint (i.e. update past values based on future data), and the number of periods used to calculate the EMA and signal lines. The f_security() function calls the request.security() function to fetch data from the specified security and timeframe, and is used to calculate the EMA and signal lines using the ta.ema() function. The clo variable is assigned the closing price data, adjusted for repainting and timeframe. The EMA line is calculated using a weighted average of the EMA over the specified period and two times that period, as well as three times that period, divided by six. The signal line is calculated as the EMA of the EMA line over the specified period. The col_css variable sets the color of the EMA line based on whether it is currently above or below the signal line. The script then plots the EMA and signal lines, and uses the plotshape() function to indicate long and short signals based on the crossovers and crossunders of the EMA and signal lines. Finally, the script sets up alert conditions using the alertcondition() function to notify the user when a long or short signal is generated, including information about the symbol and closing price. █  SPECIAL THANKS Special thanks to LOXX, I wanted to take a moment to express my gratitude for his valuable input in the EMA calculation. His insights and expertise have greatly helped me in improving my Pine Script coding skills. Thanks to his suggestion, I was able to better understand the EMA formula and implement it effectively in my script. Your generosity in sharing your knowledge and experience is truly appreciated. It is through collaboration and exchanging ideas that we can all grow and become better in our craft. This script provides exact signals that, with suitable additional indicators, provide very good results. Best regards Chervolino
Penunjuk Pine Script®
oleh chervolino
kNNLibrary "kNN" Collection of experimental kNN functions. This is a work in progress, an improvement upon my original kNN script: The script can be recreated with this library. Unlike the original script, that used multiple arrays, this has been reworked with the new Pine Script matrix features. To make a kNN prediction, the following data should be supplied to the wrapper: kNN : filter type. Right now either Binary or Percent . Binary works like in the original script: the system stores whether the price has increased (+1) or decreased (-1) since the previous knnStore event (called when either long or short condition is supplied). Percent works the same, but the values stored are the difference of prices in percents. That way larger differences in prices would give higher scores. k : number k. This is how many nearest neighbors are to be selected (and summed up to get the result). skew : kNN minimum difference. Normally, the prediction is done with a simple majority of the neighbor votes. If skew is given, then more than a simple majority is needed for a prediction. This also means that there are inputs for which no prediction would be given (if the majority votes are between -skew and +skew). Note that in Percent mode more profitable trades will have higher voting power. depth : kNN matrix size limit. Originally, the whole available history of trades was used to make a prediction. This not only requires more computational power, but also neglects the fact that the market conditions are changing. This setting restricts the memory matrix to a finite number of past trades. price : price series long : long condition. True if the long conditions are met, but filters are not yet applied. For example, in my original script, trades are only made on crossings of fast and slow MAs. So, whenever it is possible to go long, this value is set true. False otherwise. short : short condition. Same as long , but for short condition. store : whether the inputs should be stored. Additional filters may be applied to prevent bad trades (for example, trend-based filters), so if you only need to consult kNN without storing the trade, this should be set to false. feature1 : current value of feature 1. A feature in this case is some kind of data derived from the price. Different features may be used to analyse the price series. For example, oscillator values. Not all of them may be used for kNN prediction. As the current kNN implementation is 2-dimensional, only two features can be used. feature2 : current value of feature 2. The wrapper returns a tuple: [ longOK, shortOK ]. This is a pair of filters. When longOK is true, then kNN predicts a long trade may be taken. When shortOK is true, then kNN predicts a short trade may be taken. The kNN filters are returned whenever long or short conditions are met. The trade is supposed to happen when long or short conditions are met and when the kNN filter for the desired direction is true. Exported functions : knnStore(knn, p1, p2, src, maxrows)   Store the previous trade; buffer the current one until results are in. Results are binary: up/down   Parameters:      knn : knn matrix      p1 : feature 1 value      p2 : feature 2 value      src : current price      maxrows : limit the matrix size to this number of rows (0 of no limit)   Returns: modified knn matrix knnStorePercent(knn, p1, p2, src, maxrows)   Store the previous trade; buffer the current one until results are in. Results are in percents   Parameters:      knn : knn matrix      p1 : feature 1 value      p2 : feature 2 value      src : current price      maxrows : limit the matrix size to this number of rows (0 of no limit)   Returns: modified knn matrix knnGet(distance, result)   Get neighbours by getting k results with the smallest distances   Parameters:      distance : distance array      result : result array   Returns: array slice of k results knnDistance(knn, p1, p2)   Create a distance array from the two given parameters   Parameters:      knn : knn matrix      p1 : feature 1 value      p2 : feature 2 value   Returns: distance array knnSum(knn, p1, p2, k)   Make a prediction, finding k nearest neighbours and summing them up   Parameters:      knn : knn matrix      p1 : feature 1 value      p2 : feature 2 value      k : sum k nearest neighbors   Returns: sum of k nearest neighbors doKNN(kNN, k, skew, depth, price, long, short, store, feature1, feature2)   execute kNN filter   Parameters:      kNN : filter type      k : number k      skew : kNN minimum difference      depth : kNN matrix size limit      price : series      long : long condition      short : short condition      store : store the supplied features (if false, only checks the results without storage)      feature1 : feature 1 value      feature2 : feature 2 value   Returns: filter output
Perpustakaan Pine Script®
oleh lastguru
5
DMI + HMA - No Risk ManagementDMI (Directional Movement Index) and HMA (Hull Moving Average) The DMI and HMA make a great combination, The DMI will gauge the market direction, while the HMA will add confirmation to the trend strength. What is the DMI? The DMI is an indicator that was developed by J. Welles Wilder in 1978. The Indicator was designed to identify in which direction the price is moving. This is done by comparing previous highs and lows and drawing 2 lines. 1. A Positive movement line 2. A Negative movement line A third line can be added, which would be known as the ADX line or Average Directional Index. This can also be used to gauge the strength in which direction the market is moving. When the Positive movement line (DI+) is above the Negative movement line (DI-) there is more upward pressure. Ofcourse visa versa, when the DI- is above the DI+ that would indicate more downwards pressure. Want to know more about HMA? Check out one of our other published scripts What is this strategy doing? We are first waiting for the DMI to cross in our favoured direction, after that, we wait for the HMA to signal the entry. Without both conditions being true, no trade will be made. Long Entries 1. DI+ crosses above DI- 2. HMA line 1 is above HMA line 2 Short Entries 1. DI- Crosses above DI+ 2. HMA line 1 is below HMA lilne 2 Its as simple as that. Conclusion While this strategy does have its downsides, that can be reduced by adding some risk manegment into the script. In general the trade profitability is above average, And the max drawdown is at a minimum. The settings have been optimised to suite BTCUSDT PERP markets. Though with small adjustments it can be used on many assets!
Strategi Pine Script®
oleh Tuned_Official
1
Strat AssistantStrat Assistant This script will help you follow the strat.  While other collections of scripts exist to do similar functionality, the idea of this (work in progress) is to be a one stop shop for all things strat that will evolve over time. Fairly new to the strat and pine script.  The script is for informational purposes only.  Please do you due diligence. Features: =Candle numbering: will number candles underneath based on the prior candle.  1 for an inside bar 2 for a directional bar (up or down) and 3 for an outside bar.  =Candle coloring: will highlight candles.  Yellow for an inside candle, magenta for an outside candle, red for a 2 down candle, green for a 2 up candle.  It will not modify the outside border of the candle so you can still see green if the open was lower than the close or red if the close was below open.   =Candle shape: will place an arrow up if the 2 candle is a directional UP and arrows down if the 2 candle is a directional DOWN.  It will display red if it's bearish and green if it's bullish.   =Strat combos: will provide a text description of all currently applicable strat combinations if they are active at the top right of the chart. It will display red if it's bearish and green if it's bullish.   =Actionable signals: will provide text description of actionable signals if they are active on the bottom right of the chart. Inside bar if the bar is inside the prior bar, the color of this signal will be blue (shows better on white background). Hammer will be 75% of the candle is at the bottom and the open and close are above the 75% of the wick. Hammers will display green for bullish. Shooters are just the opposite of hammers, 75% of the wick is at the top and the open and close are below 75% of the wick. Shooters will display at red for bearish. =Time Frame Continuity: will provide time frame continuity across 15m, 30m, Hour, Day, Week, Quarter, Year with green arrows up if the close is above the open for the given time frame, or red arrows down if the close is below the open for the given time frame. This will also look to determine if the time frame is applicable based on what time frame the user selects as well as ensures history exists for the given time frame. Backlog / Work in progress: =Opacity for time frame continuity =Line indicators (or maybe just a label) for highs and lows of previous periods (hour, day, week, quarter) =Alert conditions =User input for various indicators
Penunjuk Pine Script®
oleh rickyzcarroll
59
McGinley Dynamic (Improved) - John R. McGinley, Jr.For all the McGinley enthusiasts out there, this is my improved version of the "McGinley Dynamic", originally formulated and publicized in 1990 by John R. McGinley, Jr. Prior to this release, I recently had an encounter with a member request regarding the reliability and stability of the general algorithm. Years ago, I attempted to discover the root of it's inconsistency, but success was not possible until now. Being no stranger to a good old fashioned computational crisis, I revisited it with considerable contemplation. I discovered a lack of constraints in the formulation that either caused the algorithm to implode to near zero and zero OR it could explosively enlarge to near infinite values during unusual price action volatility conditions, occurring on different time frames. A numeric E-notation in a moving average doesn't mean a stock just shot up in excess of a few quintillion in value from just "10ish" moments ago. Anyone experienced with the usual McGinley Dynamic, has probably encountered this with dynamically dramatic surprises in their chart, destroying it's usability. Well, I believe I have found an answer to this dilemma of 'susceptibility to miscalculation', to provide what is most likely McGinley's whole hearted intention. It required upgrading the formulation with two constraints applied to it using min/max() functions. Let me explain why below. When using base numbers with an exponent to the power of four, some miniature numbers smaller than one can numerically collapse to near 0 values, or even 0.0 itself. A denominator of zero will always give any computational device a horribly bad day, not to mention the developer. Let this be an EASY lesson in computational division, I often entertainingly express to others. You have heard the terminology "$#|T happens!🙂" right? In the programming realm, "AnyNumber/0.0 CAN happen!🤪" too, and it happens "A LOT" unexpectedly, even when it's highly improbable. On the other hand, numbers a bit larger than 2 with the power of four can tremendously expand rapidly to the numeric limits of 64-bit processing, generating ginormous spikes on a chart. The ephemeral presence of one OR both of those potentials now has a combined satisfactory remedy, AND you as TV members now have it, endowed with the ever evolving "Power of Pine". Oh yeah, this one plots from bar_index==0 too. It also has experimental settings tweaks to play with, that may reveal untapped potential of this formulation. This function now has gain of function capabilities, NOT to be confused with viral gain of function enhancements from reckless BSL-4 leaking laboratories that need to be eternally abolished from this planet. Although, I do have hopes this imd() function has the potential to go viral. I believe this improved function may have utility in the future by developers of the TradingView community. You have the source, and use it wisely... I included an generic ema() plot for a basic comparison, ultimately unveiling some of this algorithm's unique characteristics differing on a variety of time frames. Also another unconstrained function is included to display some the disparities of having no limitations on a divisor in the calculation. I strongly advise against the use of umd() in any published script. There is simply just no reason to even ponder using it. I also included notes in the script to warn against this. It's funny now, but some folks don't always read/understand my advisories... You have been warned! NOTICE: You have absolute freedom to use this source code any way you see fit within your new Pine projects, and that includes TV themselves. You don't have to ask for my permission to reuse this improved function in your published scripts, simply because I have better things to do than answer requests for the reuse of this simplistic imd() function. Sufficient accreditation regarding this script and compliance with "TV's House Rules" regarding code reuse, is as easy as copying the entire function as is. Fair enough? Good! I have a backlog of "computational crises" to contend with, including another one during the writing of this elaborate description. When available time provides itself, I will consider your inquiries, thoughts, and concepts presented below in the comments section, should you have any questions or comments regarding this indicator. When my indicators achieve more prevalent use by TV members, I may implement more ideas when they present themselves as worthy additions. Have a profitable future everyone!
Penunjuk Pine Script®
oleh ImmortalFreedom
42
Laguerre Multi-Filter [DW]This is an experimental study designed to identify underlying price activity using a series of Laguerre Filters. Two different modes are included within this script: -Ribbon Mode - A ribbon of 18 Laguerre Filters with separate Gamma values is calculated. -Band Mode - An average of the 18 filters generates the basis line. Then, Golden Mean ATR over the specified sampling period multiplied by 1 and 2 are added and subtracted to the basis line to generate the bands. Multi-Timeframe functionality is included. You can choose any timeframe that TradingView supports as the basis resolution for the script. Custom bar colors are included. Bar colors are based on the direction of any of the 18 filters, or the average filter's direction in Ribbon Mode. In Band Mode, the colors are based solely on the average filter's direction.
Penunjuk Pine Script®
oleh DonovanWall
7
TextLibrary "Text" library to format text in different fonts or cases plus a sort function. 🔸 Credits and Usage This library is inspired by the work of three authors (in chronological order of publication date): Unicode font function - JD - Duyck UnicodeReplacementFunction - wlhm font - kaigouthro 🔹 Fonts Besides extra added font options, the toFont(fromText, font) method uses a different technique. On the first runtime bar (whether it is barstate.isfirst , barstate.islast , or between) regular letters and numbers and mapped with the chosen font. After this, each character is replaced using the build-in key - value pair map function . Also an enum Efont is included. Note: Some fonts are not complete, for example there isn't a replacement for every character in Superscript/Subscript. Example of usage (besides the included table example): import fikira/Text/1 as t i_font = input.enum(t.Efont.Blocks) if barstate.islast sentence = "this sentence contains words" label.new(bar_index, 0, t.toFont(fromText = sentence, font = str.tostring(i_font)), style=label.style_label_lower_right) label.new(bar_index, 0, t.toFont(fromText = sentence, font = "Circled" ), style=label.style_label_lower_left ) label.new(bar_index, 0, t.toFont(fromText = sentence, font = "Wiggly" ), style=label.style_label_upper_right) label.new(bar_index, 0, t.toFont(fromText = sentence, font = "Upside Latin" ), style=label.style_label_upper_left ) 🔹 Cases The script includes a toCase(fromText, case) method to transform text into snake_case, UPPER SNAKE_CASE, kebab-case, camelCase or PascalCase, as well as an enum Ecase . Example of usage (besides the included table example): import fikira/Text/1 as t i_case = input.enum(t.Ecase.camel) if barstate.islast sentence = "this sentence contains words" label.new(bar_index, 0, t.toCase(fromText = sentence, case = str.tostring(i_case)), style=label.style_label_lower_right) label.new(bar_index, 0, t.toCase(fromText = sentence, case = "snake_case" ), style=label.style_label_lower_left ) label.new(bar_index, 0, t.toCase(fromText = sentence, case = "PascalCase" ), style=label.style_label_upper_right) label.new(bar_index, 0, t.toCase(fromText = sentence, case = "SNAKE_CASE" ), style=label.style_label_upper_left ) 🔹 Sort The sort(strings, order, sortByUnicodeDecimalNumbers) method returns a sorted array of strings. strings: array of strings, for example words = array.from("Aword", "beyond", "Space", "salt", "pepper", "swing", "someThing", "otherThing", "12345", "_firstWord") order: "asc" / "desc" (ascending / descending) sortByUnicodeDecimalNumbers: true/false; default = false _____ • sortByUnicodeDecimalNumbers: every Unicode character is linked to a Unicode Decimal number ( wikipedia.org/wiki/List_of_Unicode_characters ), for example: 1 49 2 50 3 51 ... A 65 B 66 ... S 83 ... _ 95 ` 96 a 97 b 98 ... o 111 p 112 q 113 r 114 s 115 ... This means, if we sort without adjusting ( sortByUnicodeDecimalNumbers = true ), in ascending order, the letter b (98 - small) would be after S (83 - Capital). By disabling sortByUnicodeDecimalNumbers , Capital letters are intermediate transformed to str.lower() after which the Unicode Decimal number is retrieved from the small number instead of the capital number. For example S (83) -> s (115), after which the number 115 is used to sort instead of 83. Example of usage (besides the included table example): import fikira/Text/1 as t if barstate.islast aWords = array.from("Aword", "beyond", "Space", "salt", "pepper", "swing", "someThing", "otherThing", "12345", "_firstWord") label.new(bar_index, 0, str.tostring(t.sort(strings= aWords, order = 'asc' , sortByUnicodeDecimalNumbers = false)), style=label.style_label_lower_right) label.new(bar_index, 0, str.tostring(t.sort(strings= aWords, order = 'desc', sortByUnicodeDecimalNumbers = false)), style=label.style_label_lower_left ) label.new(bar_index, 0, str.tostring(t.sort(strings= aWords, order = 'asc' , sortByUnicodeDecimalNumbers = true )), style=label.style_label_upper_right) label.new(bar_index, 0, str.tostring(t.sort(strings= aWords, order = 'desc', sortByUnicodeDecimalNumbers = true )), style=label.style_label_upper_left ) 🔸 Methods/functions method toFont(fromText, font)   toFont : Transforms text into the selected font   Namespace types: series string, simple string, input string, const string   Parameters:      fromText (string)      font (string)   Returns: `fromText` transformed to desired `font` method toCase(fromText, case)   toCase : formats text to snake_case, UPPER SNAKE_CASE, kebab-case, camelCase or PascalCase   Namespace types: series string, simple string, input string, const string   Parameters:      fromText (string)      case (string)   Returns: `fromText` formatted to desired `case` method sort(strings, order, sortByUnicodeDecimalNumbers)   sort : sorts an array of strings, ascending/descending and by Unicode Decimal numbers or not.   Namespace types: array   Parameters:      strings (array)      order (string)      sortByUnicodeDecimalNumbers (bool)   Returns: Sorted array of strings
Perpustakaan Pine Script®
oleh fikira
2
Follow Line Strategy Version 2.5 (React HTF)Follow Line Strategy v2.5 (React HTF) - TradingView Script Usage This strategy utilizes a "Follow Line" concept based on Bollinger Bands and ATR to identify potential trading opportunities. It includes advanced features like optional working hours filtering, higher timeframe (HTF) trend confirmation, and improved trend-following entry/exit logic. Version 2.5 introduces reactivity to HTF trend changes for more adaptive trading. Key Features: Follow Line: The core of the strategy. It dynamically adjusts based on price breakouts beyond Bollinger Bands, using either the low/high or ATR-adjusted levels. Bollinger Bands: Uses a standard Bollinger Bands setup to identify overbought/oversold conditions. ATR Filter: Optionally uses the Average True Range (ATR) to adjust the Follow Line offset, providing a more dynamic and volatility-adjusted entry point. Optional Trading Session Filter: Allows you to restrict trading to specific hours of the day. Higher Timeframe (HTF) Confirmation: A significant feature that allows you to confirm trade signals with the trend on a higher timeframe. This can help to filter out false signals and improve the overall win rate. HTF Selection Method: Choose between Auto and Manual HTF selection: Auto: The script automatically determines the appropriate HTF based on the current chart timeframe (e.g., 1min -> 15min, 5min -> 4h, 1h -> 1D, Daily -> Monthly). Manual: Allows you to select a specific HTF using the Manual Higher Timeframe input. Trend-Following Entries/Exits: The strategy aims to enter trades in the direction of the established trend, using the Follow Line to define the trend. Reactive HTF Trend Changes: v2.5 exits positions not only based on the trade timeframe (TTF) trend changing, but also when the higher timeframe trend reverses against the position. This makes the strategy more responsive to larger market movements. Alerts: Provides buy and sell alerts for convenient trading signal notifications. Visualizations: Plots the Follow Line for both the trade timeframe and the higher timeframe (optional), making it easy to understand the strategy's logic. How to Use: Add to Chart: Add the "Follow Line Strategy Version 2.5 (React HTF)" script to your TradingView chart. Configure Settings: Customize the strategy's settings to match your trading style and preferences. Here's a breakdown of the key settings: Indicator Settings: ATR Period: The period used to calculate the ATR. A smaller period is more sensitive to recent price changes. Bollinger Bands Period: The period used for the Bollinger Bands calculation. A longer period results in smoother bands. Bollinger Bands Deviation: The number of standard deviations from the moving average that the Bollinger Bands are plotted. Higher deviations create wider bands. Use ATR for Follow Line Offset?: Enable to use ATR to calculate the Follow Line offset. Disable to use the simple high/low. Show Trade Signals on Chart?: Enable to show BUY/SELL labels on the chart. Time Filter: Use Trading Session Filter?: Enable to restrict trading to specific hours of the day. Trading Session: The trading session to use (e.g., 0930-1600 for regular US stock market hours). Use 0000-2400 for all hours. Higher Timeframe Confirmation: Enable HTF Confirmation?: Enable to use the HTF trend to filter trade signals. If enabled, only trades in the direction of the HTF trend will be taken. HTF Selection Method: Choose between "Auto" and "Manual" HTF selection. Manual Higher Timeframe: If "Manual" is selected, choose the specific HTF (e.g., 240 for 4 hours, D for daily). Show HTF Follow Line?: Enable to plot the HTF Follow Line on the chart. Understanding the Signals: Buy Signal: The price breaks above the upper Bollinger Band, and the HTF (if enabled) confirms the uptrend. Sell Signal: The price breaks below the lower Bollinger Band, and the HTF (if enabled) confirms the downtrend. Exit Long: The trade timeframe trend changes to downtrend or the higher timeframe trend changes to downtrend. Exit Short: The trade timeframe trend changes to uptrend or the higher timeframe trend changes to uptrend. Alerts: The script includes alert conditions for buy and sell signals. To set up alerts, click the "Alerts" button in TradingView and select the desired alert condition from the script. The alert message provides the ticker and interval. Backtesting and Optimization: Use TradingView's Strategy Tester to backtest the strategy on different assets and timeframes. Experiment with different settings to optimize the strategy for your specific trading style and risk tolerance. Pay close attention to the ATR Period, Bollinger Bands settings, and the HTF confirmation options. Tips and Considerations: HTF Confirmation: The HTF confirmation can significantly improve the strategy's performance by filtering out false signals. However, it can also reduce the number of trades. Risk Management: Always use proper risk management techniques, such as stop-loss orders and position sizing, when trading any strategy. Market Conditions: The strategy may perform differently in different market conditions. It's important to backtest and optimize the strategy for the specific markets you are trading. Customization: Feel free to modify the script to suit your specific needs. For example, you could add additional filters or entry/exit conditions. Pyramiding: The pyramiding = 0 setting prevents multiple entries in the same direction, ensuring the strategy doesn't compound losses. You can adjust this value if you prefer to pyramid into winning positions, but be cautious. Lookahead: The lookahead = barmerge.lookahead_off setting ensures that the HTF data is calculated based on the current bar's closed data, preventing potential future peeking bias. Trend Determination: The logic for determining the HTF trend and reacting to changes is critical. Carefully review the f_calculateHTFData function and the conditions for exiting positions to ensure you understand how the strategy responds to different market scenarios. Disclaimer: This script is for informational and educational purposes only. It is not financial advice, and you should not trade based solely on the signals generated by this script. Always do your own research and consult with a qualified financial advisor before making any trading decisions. The author is not responsible for any losses incurred as a result of using this script.
Strategi Pine Script®
oleh fenyesk
Buy&Sell Hollow CandlesThe Hollow Candles Script is a type of candlestick analysis script designed to highlight the following: Purpose of the Script: This script provides the user with buy and sell signals based on candlesticks that show an upward or downward reversal. Mechanism of the Script: When a hollow (unfilled) red candle appears, it signals a potential entry, provided that this candle is at a low point, following a series of red candles with higher volume than previous days. Similarly, it gives a sell signal when a green candle appears at a peak with high sell volume surpassing that of prior days. However, the appearance of these candles alone should not prompt an immediate buy or sell; you should wait for a confirming candle to validate the signal. Sideways Movement Caution: If these signals appear during a sideways or flat trend, it is not advisable to proceed with buying or selling. Chart Insights: The chart demonstrates certain buy and sell operations along with some non-ideal signals where decision-making should be based on fundamental analytical experience.
Penunjuk Pine Script®
oleh ADXAE
Value at Risk [OmegaTools]The "Value at Risk" (VaR) indicator is a powerful financial risk management tool that helps traders estimate the potential losses in a portfolio over a specified period of time, given a certain level of confidence. VaR is widely used by financial institutions, traders, and risk managers to assess the probability of portfolio losses in both normal and volatile market conditions. This TradingView script implements a comprehensive VaR calculation using several models, allowing users to visualize different risk scenarios and adjust their trading strategies accordingly. Concept of Value at Risk Value at Risk (VaR) is a statistical technique used to measure the likelihood of losses in a portfolio or financial asset due to market risks. In essence, it answers the question: "What is the maximum potential loss that could occur in a given portfolio over a specific time horizon, with a certain confidence level?" For instance, if a portfolio has a one-day 95% VaR of $10,000, it means that there is a 95% chance the portfolio will not lose more than $10,000 in a single day. Conversely, there is a 5% chance of losing more than $10,000. VaR is a key risk management tool for portfolio managers and traders because it quantifies potential losses in monetary terms, allowing for better-informed decision-making. There are several ways to calculate VaR, and this indicator script incorporates three of the most commonly used models: Historical VaR: This approach uses historical returns to estimate potential losses. It is based purely on past price data, assuming that the past distribution of returns is indicative of future risks. Variance-Covariance VaR: This model assumes that asset returns follow a normal distribution and that the risk can be summarized using the mean and standard deviation of past returns. It is a parametric method that is widely used in financial risk management. Exponentially Weighted Moving Average (EWMA) VaR: In this model, recent data points are given more weight than older data. This dynamic approach allows the VaR estimation to react more quickly to changes in market volatility, which is particularly useful during periods of market stress. This model uses the Exponential Weighted Moving Average Volatility Model. How the Script Works The script starts by offering users a set of customizable input settings. The first input allows the user to choose between two main calculation modes: "All" or "OCT" (Only Current Timeframe). In the "All" mode, the script calculates VaR using all available methodologies—Historical, Variance-Covariance, and EWMA—providing a comprehensive risk overview. The "OCT" mode narrows the calculation to the current timeframe, which can be particularly useful for intraday traders who need a more focused view of risk. The next input is the lookback window, which defines the number of historical periods used to calculate VaR. Commonly used lookback periods include 21 days (approximately one month), 63 days (about three months), and 252 days (roughly one year), with the script supporting up to 504 days for more extended historical analysis. A longer lookback period provides a more comprehensive picture of risk but may be less responsive to recent market conditions. The confidence level is another important setting in the script. This represents the probability that the loss will not exceed the VaR estimate. Standard confidence levels are 90%, 95%, and 99%. A higher confidence level results in a more conservative risk estimate, meaning that the calculated VaR will reflect a more extreme loss scenario. In addition to these core settings, the script allows users to customize the visual appearance of the indicator. For example, traders can choose different colors for "Bullish" (Risk On), "Bearish" (Risk Off), and "Neutral" phases, as well as colors for highlighting "Breaks" in the data, where returns exceed the calculated VaR. These visual cues make it easy to identify periods of heightened risk at a glance. The actual VaR calculation is broken down into several models, starting with the Historical VaR calculation. This is done by computing the logarithmic returns of the asset's closing prices and then using linear interpolation to determine the percentile corresponding to the desired confidence level. This percentile represents the potential loss in the asset over the lookback period. Next, the script calculates Variance-Covariance VaR using the mean and standard deviation of the historical returns. The standard deviation is multiplied by a z-score corresponding to the chosen confidence level (e.g., 1.645 for 95% confidence), and the resulting value is subtracted from the mean return to arrive at the VaR estimate. The EWMA VaR model uses the EWMA for the sigma parameter, the standard deviation, obtaining a specific dynamic in the volatility. It is particularly useful in volatile markets where recent price behavior is more indicative of future risk than older data. For traders interested in intraday risk management, the script provides several methods to adjust VaR calculations for lower timeframes. By using intraday returns and scaling them according to the chosen timeframe, the script provides a dynamic view of risk throughout the trading day. This is especially important for short-term traders who need to manage their exposure during high-volatility periods within the same day. The script also incorporates an EWMA model for intraday data, which gives greater weight to the most recent intraday price movements. In addition to calculating VaR, the script also attempts to detect periods where the asset's returns exceed the estimated VaR threshold, referred to as "Breaks." When the returns breach the VaR limit, the script highlights these instances on the chart, allowing traders to quickly identify periods of extreme risk. The script also calculates the average of these breaks and displays it for comparison, helping traders understand how frequently these high-risk periods occur. The script further visualizes the risk scenario using a risk phase classification system. Depending on the level of risk, the script categorizes the market as either "Risk On," "Risk Off," or "Risk Neutral." In "Risk On" mode, the market is considered bullish, and the indicator displays a green background. In "Risk Off" mode, the market is bearish, and the background turns red. If the market is neither strongly bullish nor bearish, the background turns neutral, signaling a balanced risk environment. Traders can customize whether they want to see this risk phase background, along with toggling the display of the various VaR models, the intraday methods, and the break signals. This flexibility allows traders to tailor the indicator to their specific needs, whether they are day traders looking for quick intraday insights or longer-term investors focused on historical risk analysis. The "Risk On" and "Risk Off" phases calculated by this Value at Risk (VaR) script introduce a novel approach to market risk assessment, offering traders an advanced toolset to gauge market sentiment and potential risk levels dynamically. These risk phases are built on a combination of traditional VaR methodologies and proprietary logic to create a more responsive and intuitive way to manage exposure in both normal and volatile market conditions. This method of classifying market conditions into "Risk On," "Risk Off," or "Risk Neutral" is not something that has been traditionally associated with VaR, making it a groundbreaking addition to this indicator. How the "Risk On" and "Risk Off" Phases Are Calculated In typical VaR implementations, the focus is on calculating the potential losses at a given confidence level without providing an overall market outlook. This script, however, introduces a unique risk classification system that takes the output of various VaR models and translates it into actionable signals for traders, marking whether the market is in a Risk On, Risk Off, or Risk Neutral phase. The Risk On and Risk Off phases are primarily determined by comparing the current returns of the asset to the average VaR calculated across several different methods, including Historical VaR, Variance-Covariance VaR, and EWMA VaR. Here's how the process works: 1. Threshold Setting and Effect Calculation: The script first computes the average VaR using the selected models. It then checks whether the current returns (expressed as a negative value to signify loss) exceed the average VaR value. If the current returns surpass the calculated VaR threshold, this indicates that the actual market risk is higher than expected, signaling a potential shift in market conditions. 2. Break Analysis: In addition to monitoring whether returns exceed the average VaR, the script counts the number of instances within the lookback period where this breach occurs. This is referred to as the "break effect." For each period in the lookback window, the script checks whether the returns surpass the calculated VaR threshold and increments a counter. The percentage of periods where this breach occurs is then calculated as the "effect" or break percentage. 3. Dual Effect Check (if "Double" Risk Scenario is selected): When the user chooses the "Double" risk scenario mode, the script performs two layers of analysis. First, it calculates the effect of returns exceeding the VaR threshold for the current timeframe. Then, it calculates the effect for the lower intraday timeframe as well. Both effects are compared to the user-defined confidence level (e.g., 95%). If both effects exceed the confidence level, the market is deemed to be in a high-risk situation, thus triggering a Risk Off phase. If both effects fall below the confidence level, the market is classified as Risk On. 4. Risk Phases Determination: The final risk phase is determined by analyzing these effects in relation to the confidence level: - Risk On: If the calculated effect of breaks is lower than the confidence level (e.g., fewer than 5% of periods show returns exceeding the VaR threshold for a 95% confidence level), the market is considered to be in a relatively safe state, and the script signals a "Risk On" phase. This is indicative of bullish conditions where the potential for extreme loss is minimal. - Risk Off: If the break effect exceeds the confidence level (e.g., more than 5% of periods show returns breaching the VaR threshold), the market is deemed to be in a high-risk state, and the script signals a "Risk Off" phase. This indicates bearish market conditions where the likelihood of significant losses is higher. - Risk Neutral: If the break effect hovers near the confidence level or if there is no clear trend indicating a shift toward either extreme, the market is classified as "Risk Neutral." In this phase, neither bulls nor bears are dominant, and traders should remain cautious. The phase color that the script uses helps visualize these risk phases. The background will turn green in Risk On conditions, red in Risk Off conditions, and gray in Risk Neutral phases, providing immediate visual feedback on market risk. In addition to this, when the "Double" risk scenario is selected, the background will only turn green or red if both the current and intraday timeframes confirm the respective risk phase. This double-checking process ensures that traders are only given a strong signal when both longer-term and short-term risks align, reducing the likelihood of false signals. A New Way of Using Value at Risk This innovative Risk On/Risk Off classification, based on the interaction between VaR thresholds and market returns, represents a significant departure from the traditional use of Value at Risk as a pure risk measurement tool. Typically, VaR is employed as a backward-looking measure of risk, providing a static estimate of potential losses over a given timeframe with no immediate actionable feedback on current market conditions. This script, however, dynamically interprets VaR results to create a forward-looking, real-time signal that informs traders whether they are operating in a favorable (Risk On) or unfavorable (Risk Off) environment. By incorporating the "break effect" analysis and allowing users to view the VaR breaches as a percentage of past occurrences, the script adds a predictive element that can be used to time market entries and exits more effectively. This **dual-layer risk analysis**, particularly when using the "Double" scenario mode, adds further granularity by considering both current timeframe and intraday risks. Traders can therefore make more informed decisions not just based on historical risk data, but on how the market is behaving in real-time relative to those risk benchmarks. This approach transforms the VaR indicator from a risk monitoring tool into a decision-making system that helps identify favorable trading opportunities while alerting users to potential market downturns. It provides a more holistic view of market conditions by combining both statistical risk measurement and intuitive phase-based market analysis. This level of integration between VaR methodologies and real-time signal generation has not been widely seen in the world of trading indicators, marking this script as a cutting-edge tool for risk management and market sentiment analysis. I would like to express my sincere gratitude to @skewedzeta for his invaluable contribution to the final script. From generating fresh ideas to applying his expertise in reviewing the formula, his support has been instrumental in refining the outcome.
Penunjuk Pine Script®
oleh OmegaTools
3
Jason's Simple Moving Averages WaveUnderstanding the Script: Purpose: This script identifies potential trend direction and momentum using a moving average and wave amplitude calculation. It shows a green line when the price is trending upwards and a red line when trending downwards. Strategy: This script doesn't provide a complete trading strategy. It's an indicator designed to be used alongside other tools. Parameters: You can adjust the "Moving Average Length" input to change the sensitivity of the indicator. A shorter length will react quicker to price changes, while a longer length will be smoother but less responsive. How to Use it: Load the Script: In TradingView, navigate to the indicator creation section and paste the provided script code. Adjust Parameters: Set the "Moving Average Length" based on your preferred timeframe and trading style. Combine with Other Tools: Use the indicator along with other technical indicators or price action analysis to confirm potential entry and exit points for trades. Here are some additional points to consider: Crossovers: You could look for buy signals when the price crosses above the green line and sell signals when it crosses below the red line. However, these can be prone to false signals. Divergence: Look for divergences between the price movement and the wave indicator. For example, a rising price with a falling wave could indicate overbought conditions and a potential reversal. Confirmation: Don't rely solely on this indicator. Use it alongside other confirmations from price action, volume analysis, or other indicators to identify higher probability trades. Important Note:
Penunjuk Pine Script®
oleh jason_a_woods11
ET's FlagsPurpose: This Pine Script is designed for the TradingView platform to identify and visually highlight specific technical chart patterns known as "Bull Flags" and "Bear Flags" on financial charts. These patterns are significant in trading as they can indicate potential continuation trends after a brief consolidation. The script includes mechanisms to manage signal frequency through a cooldown period, ensuring that the trading signals are not excessively frequent and are easier to interpret. Functionality: Input Parameters: flagpole_length: Defines the number of bars to consider when identifying the initial surge in price, known as the flagpole. flag_length: Determines the number of bars over which the flag itself is identified, representing a period of consolidation. percent_change: Sets the minimum percentage change required to validate the presence of a flagpole. cooldown_period: Specifies the number of bars to wait before another flag can be identified, reducing the risk of overlapping signals. Percentage Change Calculation: The script calculates the percentage change between two price points using a helper function percentChange(start, end). This function is crucial for determining whether the price movement within the specified flagpole_length meets the threshold set by percent_change, thus qualifying as a potential flagpole. Flagpole Identification: Bull Flagpole: Identified by finding the lowest close price over the flagpole_length and determining if the subsequent price rise meets or exceeds the specified percent_change. Bear Flagpole: Identified by finding the highest close price over the flagpole_length and checking if the subsequent price drop is sufficient as per the percent_change. Flag Identification: After identifying a flagpole, the script assesses if the price action within the next flag_length bars consolidates in a manner that fits a flag pattern. This involves checking if the price fluctuation stays within the bounds set by the percent_change. Signal Plotting: If a bull or bear flag pattern is confirmed, and the cooldown period has passed since the last flag of the same type was identified, the script plots a visual shape on the chart: Green shapes below the price bar for Bull Flags. Red shapes above the price bar for Bear Flags. Line Drawing: For enhanced visualization, the script draws lines at the high and low prices of the flag during its formation period. This visually represents the consolidation phase of the flag pattern. Debugging Labels: The script optionally displays labels at the flag formation points, showing the exact percentage change achieved during the flagpole formation. This feature aids users in understanding why a particular segment of the price chart was identified as a flag. Compliance and Usage: This script does not automate trading but provides visual aids and potential signals based on historical price analysis. It adheres to TradingView's scripting policies by only accessing publicly available price data and user-defined parameters without executing trades or accessing any external data. Conclusion: This Pine Script is a powerful tool for traders who follow technical analysis, offering a clear, automated way to spot potential continuation patterns in the markets they monitor. By emphasizing visual clarity and reducing signal redundancy through cooldown periods, the script enhances decision-making processes for chart analysis on TradingView.
Penunjuk Pine Script®
oleh MrET
Smart Money Analysis with Golden/Death Cross [YourTradingSensei]Description of the script "Smart Money Analysis with Golden/Death Cross": This TradingView script is designed for market analysis based on the concept of "Smart Money" and includes the detection of Golden Cross and Death Cross signals. Key features of the script: Moving Averages (SMA): Two moving averages are calculated: a short-term (50 periods) and a long-term (200 periods). The intersections of these moving averages are used to determine Golden Cross and Death Cross signals. High Volume: The current trading volume is analyzed. Periods of high volume are identified when the current volume exceeds the average volume by a specified multiplier. Support and Resistance Levels: Key support and resistance levels are determined based on the highest and lowest prices over a specified period. Buy and Sell Signals: Buy and sell signals are generated based on moving average crossovers, high volume, and the closing price relative to key levels. Golden Cross and Death Cross: A Golden Cross occurs when the short-term moving average crosses above the long-term moving average. A Death Cross occurs when the short-term moving average crosses below the long-term moving average. These signals are displayed on the chart with text color changes for better visualization. Using the script: The script helps traders visualize key signals and levels, aiding in making informed trading decisions based on the behavior of major market players and technical analysis. Custom candle lighting(CCL) © 2024 by YourTradingSensei is licensed under CC BY-NC-SA 4.0. To view a copy of this license.
Penunjuk Pine Script®
oleh YourTradingSensei
2